Security infrastructure for cloud services

ABSTRACT

A framework for handling a secure interaction between components in a cloud infrastructure system that wish to transfer information between each other during processing of a customer&#39;s subscription order is described. The framework orders the security zones of components based on security levels and protects the transfer of information between components in security zones with different security levels. The assignment of a component to a security zone is based upon the sensitivity of the data handled by the components, the sensitivity of functions performed by the component, and the like.

CROSS-REFERENCES TO RELATED APPLICATIONS

The present application is a non-provisional of and claims the benefitand priority under 35 U.S.C. 119(e) of the following applications, theentire contents of which are incorporated herein by reference for allpurposes:

-   (1) U.S. Provisional Application No. 61/698,413, filed Sep. 7, 2012,    entitled TENANT AUTOMATION SYSTEM;-   (2) U.S. Provisional Application No. 61/698,459, filed Sep. 7, 2012,    entitled SERVICE DEVELOPMENT INFRASTRUCTURE; and-   (3) U.S. Provisional Application No. 61/785,299, filed Mar. 14,    2013, entitled CLOUD INFRASTRUCTURE.

BACKGROUND

The present disclosure relates to computer systems and software, andmore particularly to techniques for facilitating and automating theprovision of services in a cloud environment.

Cloud computing is a model for enabling convenient, on-demand networkaccess to a shared pool of configurable computing resources (e.g.,networks, servers, storage, applications, and services). The servicesprovided or accessed through the cloud (or network) are referred to ascloud services. There is a lot of processing that needs to be performedby a cloud service provider to make cloud services available to asubscribing customer. Due to its complexity, much of this processing isstill done manually. For example, provisioning resources for providingsuch cloud services can be a very labor intensive process.

SUMMARY

Certain embodiments of the present invention provide techniques forautomating the provisioning, managing and tracking of services providedby a cloud infrastructure system. In one embodiment, the cloudinfrastructure system stores subscription order information related toone or more services subscribed to by a customer in the cloudinfrastructure system.

In one embodiment, the cloud infrastructure system provides a frameworkfor handling the secure interaction between components in the cloudinfrastructure system that wish to transfer information between eachother during processing of a customer's subscription order. In oneembodiment, the components are assigned to various security zones. Theassignment of a component to a security zone may be based upon thesensitivity of the data handled by the components, the sensitivity offunctions performed by the component, and the like.

In one embodiment, the framework orders the security zones of componentsbased on security levels. The framework protects the transfer ofinformation between components in security zones with different securitylevels. A component in a higher security zone pushes information to acomponent in a lower security zone component and pulls information froma component in lower security zone. A component in a lower security zonemay not have direct read or write access to the data managed by acomponent in a higher security zone. Components within the same securityzone may have read or write access with respect to each other. In oneembodiment, the granularity provided by the security zones is a tradeoffbetween security and efficiency when transferring information betweentwo components where the communication between two components belongingto security zones with the same security level is faster and moreefficient than the communication between two components belonging tosecurity zones with different security levels.

Some embodiments relate to a method for providing the secure interactionbetween components in a cloud infrastructure system that wish totransfer information between each other during processing of acustomer's subscription order. The method includes storing subscriptionorder information related to services subscribed to by a customer. Themethod then includes receiving a request to transfer the informationbetween a first component and a second component in the cloudinfrastructure and determining a first security zone for the firstcomponent and a second security zone for the second component. Themethod then includes determining a first security level associated withthe first security zone and a second security level associated with thesecond security zone. Then, the method includes determining the transferof information between the first component and the second componentbased upon the first security level, the second security level, andsecurity rules information. In one embodiment, the security rulesinformation specifies rules related to the transfer of informationbetween the first component and the second component.

BRIEF DESCRIPTION OF THE DRAWINGS

Illustrative embodiments of the present invention are described indetail below with reference to the following drawing figures:

FIG. 1A is a logical view of a cloud infrastructure system according toone embodiment of the present invention.

FIG. 1B is a simplified block diagram of a hardware/software stack thatmay be used to implement a cloud infrastructure system according to anembodiment of the present invention.

FIG. 2 is a simplified block diagram of a system environment forimplementing the cloud infrastructure system shown in FIG. 1A.

FIG. 3A depicts a simplified flowchart 300 depicting processing that maybe performed by the TAS module in the cloud infrastructure system, inaccordance with an embodiment of the present invention.

FIG. 3B depicts a simplified high level diagram of one or moresub-modules in the TAS module in the cloud infrastructure system, inaccordance with an embodiment of the present invention.

FIG. 4 depicts an exemplary distributed deployment of the TAS component,according to an embodiment of the present invention.

FIG. 5 is a simplified block diagram illustrating the interactions ofthe SDI module with one or more modules in the cloud infrastructuresystem, in accordance with an embodiment of the present invention.

FIG. 6 depicts a simplified high level diagram of sub-modules of the SDImodule according to an embodiment of the present invention.

FIG. 7A depicts a simplified flowchart depicting processing that may beperformed by the SDI component in the cloud infrastructure system, inaccordance with an embodiment of the present invention.

FIG. 7B depicts a simplified block diagram showing the high-levelarchitecture of a Nuviaq system 710 and its relationships with othercloud infrastructure components according to an embodiment of thepresent invention.

FIG. 7C depicts an example sequence diagram illustrating steps of aprovisioning process using a Nuviaq system according to an embodiment ofthe present invention.

FIG. 7D depicts an example sequence diagram illustrating steps of adeployment process using a Nuviaq system according to an embodiment ofthe present invention.

FIG. 7E depicts an example of database instances provisioned for adatabase service according to an embodiment of the present invention.

FIG. 8A is a logical view of the assignment of security zones to variouscomponents in the cloud infrastructure system in accordance with oneembodiment of the present invention.

FIG. 8B illustrates a security zone-based security infrastructureaccording to an embodiment of the present invention.

FIG. 9 depicts a simplified flowchart depicting processing that may beperformed by security infrastructure in cloud infrastructure system, inaccordance with an embodiment of the present invention.

FIG. 10 is a simplified block diagram of a computing system that may beused in accordance with embodiments of the present invention.

DETAILED DESCRIPTION

In the following description, for the purposes of explanation, specificdetails are set forth in order to provide a thorough understanding ofembodiments of the invention. However, it will be apparent that variousembodiments may be practiced without these specific details. The figuresand description are not intended to be restrictive.

Certain embodiments of the present invention provide techniques forautomating the provisioning, managing and tracking of services providedby a cloud infrastructure system.

In certain embodiments, a cloud infrastructure system may include asuite of applications, middleware and database service offerings thatare delivered to a customer in a self-service, subscription-based,elastically scalable, reliable, highly available, and secure manner. Anexample of such a cloud infrastructure system is the Oracle Public Cloudprovided by the present assignee.

A cloud infrastructure system may provide many capabilities including,but not limited to, provisioning, managing and tracking a customer'ssubscription for services and resources in the cloud infrastructuresystem, providing predictable operating expenses to customers utilizingthe services in the cloud infrastructure system, providing robustidentity domain separation and protection of a customer's data in thecloud infrastructure system, providing customers with a transparentarchitecture and control of the design of the cloud infrastructuresystem, providing customers assured data protection and compliance withdata privacy standards and regulations, providing customers with anintegrated development experience for building and deploying services inthe cloud infrastructure system and providing customers with a seamlessintegration between business software, middleware, database andinfrastructure services in the cloud infrastructure system.

In certain embodiments, services provided by the cloud infrastructuresystem may include a host of services that are made available to usersof the cloud infrastructure system on demand such as online data storageand backup solutions, Web-based e-mail services, hosted office suitesand document collaboration services, database processing, managedtechnical support services and the like. Services provided by the cloudinfrastructure system can dynamically scale to meet the needs of itsusers. A specific instantiation of a service provided by cloudinfrastructure system is referred to herein as a service instance. Ingeneral, any service made available to a user via a communicationnetwork such as the Internet from a cloud service provider's system isreferred to as a cloud service. Typically, in a public cloudenvironment, servers and systems that make up the cloud serviceprovider's system are different from the customer's own on-premisesservers and systems. For example, a cloud service provider's system mayhost an application and a user may, via a communication network such asthe Internet, on demand, order and use the application.

A service in a computer network cloud infrastructure includes protectedcomputer network access to storage, a hosted database, a hosted webserver, a software application, or other service provided by a cloudvendor to a user, or as otherwise known in the art. For example, aservice can include password-protected access to remote storage on thecloud through the Internet. As another example, a service can include aweb service-based hosted relational database and script-languagemiddleware engine for private use by a networked developer. As anotherexample, a service can include access to an email software applicationhosted on a cloud vendor's web site.

FIG. 1A is a logical view of a cloud infrastructure system according toone embodiment of the present invention. Cloud infrastructure system 100may provide a variety of services via a cloud or networked environment.These services may include one or more services provided under Softwareas a Service (SaaS) category, Platform as a Service (PaaS) category,Infrastructure as a Service (IaaS) category, or other categories ofservices including hybrid services. A customer, via a subscriptionorder, may order one or more services provided by cloud infrastructuresystem 100. Cloud infrastructure system 100 then performs processing toprovide the services in the customer's subscription order.

Cloud infrastructure system 100 may provide the cloud services viadifferent deployment models. For example, services may be provided undera public cloud model where cloud infrastructure system 100 is owned byan organization selling cloud services (e.g., owned by Oracle) and theservices are made available to the general public or different industryenterprises. As another example, services may be provided under aprivate cloud model where cloud infrastructure system 100 is operatedsolely for a single organization and may provide services for one ormore entities within the organization. The cloud services may also beprovided under a community cloud model where cloud infrastructure system100 and the services provided by system 100 are shared by severalorganizations in a related community. The cloud services may also beprovided under a hybrid cloud model, which is a combination of two ormore different models.

As shown in FIG. 1A, cloud infrastructure system 100 may comprisemultiple components, which working in conjunction, enable provision ofservices provided by cloud infrastructure system 100. In the embodimentillustrated in FIG. 1A, cloud infrastructure system 100 includes a SaaSplatform 102, a PaaS platform 104, an IaaS platform 110, infrastructureresources 106, and cloud management functionality 108. These componentsmay be implemented in hardware, or software, or combinations thereof.

SaaS platform 102 is configured to provide cloud services that fallunder the SaaS category. For example, SaaS platform 102 may providecapabilities to build and deliver a suite of on-demand applications onan integrated development and deployment platform. SaaS platform 102 maymanage and control the underlying software and infrastructure forproviding the SaaS services. By utilizing the services provided by SaaSplatform 102, customers can utilize applications executing on cloudinfrastructure system 100. Customers can acquire the applicationservices without the need for customers to purchase separate licensesand support.

Various different SaaS services may be provided. Examples includewithout limitation services that provide solutions for sales performancemanagement, enterprise integration and business flexibility for largeorganizations, and the like. In one embodiment, the SaaS services mayinclude Customer Relationship Management (CRM) services 110 (e.g.,Fusion CRM services provided by the Oracle cloud), Human CapitalManagement (HCM)/Talent Management services 112, and the like. CRMservices 110 may include services directed to reporting and managementof a sales activity cycle to a customer, and others. HCM/Talent services112 may include services directed to providing global workforcelifecycle management and talent management services to a customer.

Various different PaaS services may be provided by PaaS platform 104 ina standardized, shared and elastically scalable application developmentand deployment platform. Examples of PaaS services may include withoutlimitation services that enable organizations (such as Oracle) toconsolidate existing applications on a shared, common architecture, aswell as the ability to build new applications that leverage the sharedservices provided by the platform. PaaS platform 104 may manage andcontrol the underlying software and infrastructure for providing thePaaS services. Customers can acquire the PaaS services provided by cloudinfrastructure system 100 without the need for customers to purchaseseparate licenses and support. Examples of PaaS services include withoutlimitation Oracle Java Cloud Service (JCS), Oracle Database CloudService (DBCS), and others.

By utilizing the services provided by PaaS platform 104, customers canutilize programming languages and tools supported by cloudinfrastructure system 100 and also control the deployed services. Insome embodiments, PaaS services provided by the cloud infrastructuresystem 100 may include database cloud services 114, middleware cloudservices (e.g., Oracle Fusion Middleware services) 116 and Java cloudservices 117. In one embodiment, database cloud services 114 may supportshared service deployment models that enable organizations to pooldatabase resources and offer customers a database-as-a-service in theform of a database cloud, middleware cloud services 116 provides aplatform for customers to develop and deploy various businessapplications and Java cloud services 117 provides a platform forcustomers to deploy Java applications, in the cloud infrastructuresystem 100. The components in SaaS platform 102 and PaaS platform 104illustrated in FIG. 1A are meant for illustrative purposes only and arenot intended to limit the scope of embodiments of the present invention.In alternate embodiments, SaaS platform 102 and PaaS platform 104 mayinclude additional components for providing additional services to thecustomers of cloud infrastructure system 100.

Various different IaaS services may be provided by IaaS platform 110.The IaaS services facilitate the management and control of theunderlying computing resources such as storage, networks, and otherfundamental computing resources for customers utilizing servicesprovided by the SaaS platform and the PaaS platform.

In certain embodiments, cloud infrastructure system 100 includesinfrastructure resources 106 for providing the resources used to providevarious services to customers of the cloud infrastructure system 100. Inone embodiment, infrastructure resources 106 includes pre-integrated andoptimized combinations of hardware such as servers, storage andnetworking resources to execute the services provided by the PaaSplatform and the SaaS platform.

In certain embodiments, cloud management functionality 108 providescomprehensive management of cloud services (e.g., SaaS, PaaS, IaaSservices) in the cloud infrastructure system 100. In one embodiment,cloud management functionality 108 includes capabilities forprovisioning, managing and tracking a customer's subscription receivedby the cloud infrastructure system 100, and the like.

FIG. 1B is a simplified block diagram of a hardware/software stack thatmay be used to implement cloud infrastructure system 100 according to anembodiment of the present invention. It should be appreciated thatimplementation depicted in FIG. 1B may have other components than thosedepicted in FIG. 1B. Further, the embodiment shown in FIG. 1B is onlyone example of a cloud infrastructure system that may incorporate anembodiment of the invention. In some other embodiments, cloudinfrastructure system 100 may have more or fewer components than shownin FIG. 1B, may combine two or more components, or may have a differentconfiguration or arrangement of components. In certain embodiments, thehardware and software components are stacked so as to provide verticalintegration that provides optimal performance.

Various types of users may interact with cloud infrastructure system100. These users may include, for example, end users 150 that caninteract with cloud infrastructure system 100 using various clientdevices such as desktops, mobile devices, tablets, and the like. Theusers may also include developers/programmers 152 who may interact withcloud infrastructure system 100 using command line interfaces (CLIs),application programming interfaces (APIs), through various integrateddevelopment environments (IDEs), and via other applications. User mayalso include operations personnel 154. These may include personnel ofthe cloud service provider or personnel of other users.

Application services layer 156 identifies various cloud services thatmay be offered by cloud infrastructure system 100. These services may bemapped to or associated with respective software components 160 (e.g.,Oracle WebLogic server for providing Java services, oracle database forproviding database services, and the like) via a service integration andlinkages layer 158.

In certain embodiments, a number of internal services 162 may beprovided that are shared by different components or modules of cloudinfrastructure system 100 and by the services provided by cloudinfrastructure system 100. These internal shared services may include,without limitation, a security and identity service, an integrationservice, an enterprise repository service, an enterprise managerservice, a virus scanning and white list service, a high availability,backup and recovery service, service for enabling cloud support in IDEs,an email service, a notification service, a file transfer service, andthe like.

Runtime infrastructure layer 164 represents the hardware layer on whichthe various other layers and components are built. In certainembodiments, runtime infrastructure layer 164 may comprise one Oracle'sExadata machines for providing storage, processing, and networkingresources. An Exadata machine may be composed of various databaseservers, storage Servers, networking resources, and other components forhosting cloud-services related software layers. In certain embodiments,the Exadata machines may be designed to work with Oracle Exalogic, whichis an engineered system providing an assemblage of storage, compute,network, and software resources. The combination of Exadata and Exalogicprovides a complete hardware and software engineered solution thatdelivers high-performance, highly available, scalable, secure, and amanaged platform for providing cloud services.

FIG. 2 is a simplified block diagram of a system environment forimplementing the cloud infrastructure system shown in FIG. 1A accordingto an embodiment of the present invention. In the illustratedembodiment, system environment 230 includes one or more client computingdevices 224, 226 and 228 that may be used by users to interact withcloud infrastructure system 100. A client device may be configured tooperate a client application such as a web browser, a proprietary clientapplication (e.g., Oracle Forms), or some other application, which maybe used by a user of the client device to interact with cloudinfrastructure system 100 to utilize services provided by cloudinfrastructure system 100.

It should be appreciated that cloud infrastructure system 100 depictedin FIG. 2 may have other components than those depicted in FIG. 2.Further, the embodiment shown in FIG. 2 is only one example of a cloudinfrastructure system that may incorporate an embodiment of theinvention. In some other embodiments, cloud infrastructure system 100may have more or fewer components than shown in FIG. 2, may combine twoor more components, or may have a different configuration or arrangementof components.

Client computing devices 224, 226 and 228 may be general purposepersonal computers (including, by way of example, personal computersand/or laptop computers running various versions of Microsoft Windowsand/or Apple Macintosh operating systems), cell phones or PDAs (runningsoftware such as Microsoft Windows Mobile and being Internet, e-mail,SMS, Blackberry, or other communication protocol enabled), workstationcomputers running any of a variety of commercially-available UNIX orUNIX-like operating systems (including without limitation the variety ofGNU/Linux operating systems), or any other computing device. Forexample, client computing devices 224, 226 and 228 may be any otherelectronic device, such as a thin-client computer, Internet-enabledgaming system, and/or personal messaging device, capable ofcommunicating over a network (e.g., network 232 described below).Although exemplary system environment 230 is shown with three clientcomputing devices, any number of client computing devices may besupported. Other devices such as devices with sensors, etc. may interactwith cloud infrastructure system 100.

A network 232 may facilitate communications and exchange of data betweenclients 224, 226 and 228 and cloud infrastructure system 100. Network232 may be any type of network familiar to those skilled in the art thatcan support data communications using any of a variety ofcommercially-available protocols, including without limitation TCP/IP,SNA, IPX, AppleTalk, and the like. Merely by way of example, network 232can be a local area network (LAN) such as an Ethernet network, aToken-Ring network and/or the like, a wide-area network, a virtualnetwork, including without limitation a virtual private network (VPN),the Internet, an intranet, an extranet, a public switched telephonenetwork (PSTN), an infra-red network, a wireless network (e.g., anetwork operating under any of the IEEE 802.1x suite of protocols, theBluetooth protocol known in the art, and/or any other wirelessprotocol), and/or any combination of these and/or other networks.

Cloud infrastructure system 100 may comprise one or more computersand/or servers which may be general purpose computers, specializedserver computers (including, by way of example, PC servers, UNIXservers, mid-range servers, mainframe computers, rack-mounted servers,etc.), server farms, server clusters, or any other appropriatearrangement and/or combination. The computing devices that make up cloudinfrastructure system 100 may run any of operating systems or a varietyof additional server applications and/or mid-tier applications,including HTTP servers, FTP servers, CGI servers, Java servers, databaseservers, and the like. Exemplary database servers include withoutlimitation those commercially available from Oracle, Microsoft, Sybase,IBM and the like.

In various embodiments, cloud infrastructure system 100 may be adaptedto automatically provision, manage and track a customer's subscriptionto services offered by cloud infrastructure system 100. In oneembodiment, as depicted in FIG. 2, the components in cloudinfrastructure system 100 include an Identity Management (IDM) module200, a services module 202, a Tenant Automation System (TAS) module 204,a Service Deployment Infrastructure (SDI) module 206, an EnterpriseManager (EM) module 208, one or more front-end web interfaces such as astore user interface (UI) 210, a cloud user interface (UI) 212, and asupport user interface (UI) 216, an order management module 214, salespersonnel 218, operator personnel 220 and an order database 224. Thesemodules may include or be provided using one or more computers and/orservers which may be general purpose computers, specialized servercomputers, server farms, server clusters, or any other appropriatearrangement and/or combination. In one embodiment, one or more of thesemodules can be provided by cloud management functionality 108 or IaaSplatform 110 in cloud infrastructure system 100. The various modules ofthe cloud infrastructure system 100 depicted in FIG. 2 are meant forillustrative purposes only and are not intended to limit the scope ofembodiments of the present invention. Alternative embodiments mayinclude more or fewer modules than those shown in FIG. 2.

In an exemplary operation, at (1) a customer using a client device suchas client device 224 or 226 may interact with cloud infrastructuresystem 100 by browsing the various services provided by cloudinfrastructure system 100 and placing an order for a subscription forone or more services offered by cloud infrastructure system 100. Incertain embodiments, the customer may access store UI 210 or cloud UI212 and place a subscription order via these user interfaces.

The order information received by cloud infrastructure system 100 inresponse to the customer placing an order may include informationidentifying the customer and one or more services offered by the cloudinfrastructure system 100 that the customer intends to subscribe to. Asingle order may include orders for multiple services. For instance, acustomer may login to cloud UI 212 and request a subscription for a CRMservice and a Java cloud service in the same order.

Additionally, the order may also include one or more service levels forthe ordered services. As used herein, and as will be discussed ingreater detail below, a service level for a service determines theamount of resources to be allocated for providing the requested servicein the context of the subscription, such as the amount of storage,amount of computing resources, data transfer facilities, and the like.For example, a basic service level may provide a minimum level ofstorage, data transmission, or number of users, and higher servicelevels may include additional resources.

In addition, in some instances, the order information received by cloudinfrastructure system 100 may include information indicative of acustomer level, and the time period during which the service is desired.The customer level specifies the priority of the customer making thesubscription request. In one example, the priority may be determinedbased on the quality of service that the cloud infrastructure system 100guarantees or promises the customer as specified by a Service LevelAgreement (SLA) agreed to between the customer and the provider of thecloud services. In one example, the different customer levels include abasic level, a silver level and a gold level. The time period for aservice may specify the start date and time for the service and the timeperiod for which the service is desired (e.g., a service end date andtime may be specified).

In one embodiment, a customer may request a new subscription via storeUI 210 or request for a trial subscription via cloud UI 212. In certainembodiments, store UI 210 may represent the service provider's eCommercestore front (e.g., www.oracle.com/store for Oracle Cloud services).Cloud UI 212 may represent a business interface for the serviceprovider. Consumer can explore available services and sign up forinterested services through cloud UI 212. Cloud UI 212 captures userinput necessary for ordering trial subscriptions provided by cloudinfrastructure system 100. Cloud UI 212 may also be used to view accountfeatures and configure the runtime environment located within cloudinfrastructure system 100. In addition to placing an order for a newsubscription, store UI 210 may also enable the customer to perform othersubscription-related tasks such as changing the service level of asubscription, extending the term of the subscription, increasing theservice level of a subscription, terminating an existing subscription,and the like.

After an order has been placed per (1), at (2), the order informationthat is received via either store UI 210 or cloud UI 212 is stored inorder database 224, which can be one of several databases operated bycloud infrastructure system 100 and utilized in conjunction with othersystem elements. While order database 224 is shown logically as a singledatabase in FIG. 2, in actual implementation, this may comprise one ormore databases.

At (3), the order is forwarded to order management module 214. Ordermanagement module 214 is configured to perform billing and accountingfunctions related to the order such as verifying the order and uponverification, booking the order. In certain embodiments, ordermanagement module 214 may include a contract management module and aninstall base module. The contract management module may store contractinformation associated with the customer's subscription order such asthe customer's service level agreement (SLA) with cloud infrastructuresystem 100. The install base module may include detailed descriptions ofthe services in the customer's subscription order. In addition to orderinformation, the install base module may track installation detailsrelated to the services, product status and support service historyrelated to the services. As a customer orders new services or upgradesexisting ones, the install base module may automatically add new orderinformation.

At (4), information regarding the order is communicated to TAS module204. In one embodiment, TAS module 204 utilizes the order information toorchestrate the provisioning of services and resources for the orderplaced by the customer. At (5), TAS component 204 orchestrates theprovisioning of resources to support the subscribed services using theservices of SDI module 206. At (6) TAS module 204 provides informationrelated to the provisioned order received from SDI module 206 toservices module 202. In some embodiments, at (7), SDI module 206 mayalso use services provided by services module 202 to allocate andconfigure the resources needed to fulfill the customer's subscriptionorder.

At (8), services module 202 sends a notification to the customers onclient devices 224, 226 and 228 regarding the status of the order.

In certain embodiments, TAS module 204 functions as an orchestrationcomponent that manages business processes associated with each order andapplies business logic to determine whether an order should proceed toprovisioning. In one embodiment, upon receiving an order for a newsubscription, TAS module 204 sends a request to SDI module 206 toallocate resources and configure those resources needed to fulfill thesubscription order. SDI module 206 enables the allocation of resourcesfor the services ordered by the customer. SDI module 206 provides alevel of abstraction between the cloud services provided by cloudinfrastructure system 100 and the physical implementation layer that isused to provision the resources for providing the requested services.TAS module 204 may thus be isolated from implementation details such aswhether or not services and resources are actually provisioned on thefly or pre-provisioned and only allocated/assigned upon request.

In certain embodiments, a user may use store UI 210 to directly interactwith order management module 214 to perform billing and accountingrelated functions such as verifying the order and upon verification,booking the order. In some embodiments, instead of a customer placing anorder, at (9), the order may instead be placed by sales personnel 218 onbehalf of the customer such as a customer's service representative orsales representative. Sales personnel 218 may directly interact withorder management module 214 via a user interface (not shown in FIG. 2)provided by order management module 214 for placing orders or forproviding quotes for the customer. This, for example, may be done forlarge customers where the order may be placed by the customer's salesrepresentative through order management module 214. The salesrepresentative may set up the subscription on behalf of the customer.

EM module 208 is configured to monitor activities related to managingand tracking a customer's subscription in cloud infrastructure system100. EM module 208 collects usage statistics for the services in thesubscription order such as the amount of storage used, the amount datatransferred, the number of users, and the amount of system up time andsystem down time. At (10), a host operator personnel 220, who may be anemployee of a provider of cloud infrastructure system 100, may interactwith EM module 208 via an enterprise manager user interface (not shownin FIG. 2) to manage systems and resources on which services areprovisioned within cloud infrastructure system 100.

Identity management (IDM) module 200 is configured to provide identityservices such as access management and authorization services in cloudinfrastructure system 100. In one embodiment, IDM module 200 controlsinformation about customers who wish to utilize the services provided bycloud infrastructure system 100. Such information can includeinformation that authenticates the identities of such customers andinformation that describes which actions those customers are authorizedto perform relative to various system resources (e.g., files,directories, applications, communication ports, memory segments, etc.)IDM module 200 can also include the management of descriptiveinformation about each customer and about how and by whom thatdescriptive information can be accessed and modified.

In one embodiment, information managed by the identity management module200 can be partitioned to create separate identity domains. Informationbelonging to a particular identity domain can be isolated from all otheridentity domains. Also, an identity domain can be shared by multipleseparate tenants. Each such tenant can be a customer subscribing toservices in the cloud infrastructure system 100. In some embodiments, acustomer can have one or many identity domains, and each identity domainmay be associated with one or more subscriptions, each subscriptionhaving one or many services. For example, a single customer canrepresent a large entity and identity domains may be created fordivisions/departments within this large entity. EM module 208 and IDMmodule 200 may in turn interact with order management module 214 at (11)and (12) respectively to manage and track the customer's subscriptionsin cloud infrastructure system 100.

In one embodiment, at (13), support services may also be provided to thecustomer via a support UI 216. In one embodiment, support UI 216 enablessupport personnel to interact with order management module 214 via asupport backend system to perform support services at (14). Supportpersonnel in the cloud infrastructure system 100 as well as customerscan submit bug reports and check the status of these reports via supportUI 216.

Other interfaces, not shown in FIG. 2 may also be provided by cloudinfrastructure system 100. For example, an identity domain administratormay use a user interface to IDM module 200 to configure domain and useridentities. In addition, customers may log into a separate interface foreach service they wish to utilize. In certain embodiments, a customerwho wishes to subscribe to one or more services offered by cloudinfrastructure system 100 may also be assigned various roles andresponsibilities. In one embodiment, the different roles andresponsibilities that may be assigned for a customer may include that ofa buyer, an account administrator, a service administrator, an identitydomain administrator or a user who utilizes the services and resourcesoffered by cloud infrastructure system 100. The different roles andresponsibilities are described more fully in FIG. 4 below.

FIG. 3A depicts a simplified flowchart 300 depicting processing that maybe performed by the TAS module in the cloud infrastructure system, inaccordance with an embodiment of the present invention. The processingdepicted in FIG. 3A may be implemented in software (e.g., code,instructions, program) executed by one or more processors, hardware, orcombinations thereof. The software may be stored in memory (e.g., on amemory device, on a non-transitory computer-readable storage medium).The particular series of processing steps depicted in FIG. 3A is notintended to be limiting. Other sequences of steps may also be performedaccording to alternative embodiments. For example, alternativeembodiments of the present invention may perform the steps outlinedabove in a different order. Moreover, the individual steps illustratedin FIG. 3A may include multiple sub-steps that may be performed invarious sequences as appropriate to the individual step. Furthermore,additional steps may be added or removed depending on the particularapplications. One of ordinary skill in the art would recognize manyvariations, modifications, and alternatives. In one embodiment, theprocessing depicted in FIG. 3A may be performed by one or morecomponents in TAS component 204 as will be described in detail in FIG.3B.

At 302, a customer's subscription order is processed. The processing mayinclude validating the order, in one example. Validating the orderincludes ensuring that the customer has paid for the subscription andensuring that the customer does not already have subscriptions with thesame name or that the customer is not attempting to create multiplesubscriptions of the same type in the same identity domain forsubscription types for which this is disallowed (such as, in the case ofa CRM service). Processing may also include tracking the status of anorder for each order that is being processed by cloud infrastructuresystem 100.

At 304, a business process associated with the order is identified. Insome instances, multiple business processes may be identified for anorder. Each business process identifies a series of steps for processingvarious aspects of the order. As an example, a first business processmay identify one or more steps related to provisioning physicalresources for the order, a second business process may identify one ormore steps related to creating an identity domain along with customeridentities for the order, a third business process may identify one ormore steps for related to performing back office functions such ascreating a customer record for the user, performing accounting functionsrelated to the order, and the like. In certain embodiments, differentbusiness processes may also be identified for processing differentservices in an order. For example, different business process may beidentified to process a CRM service and a database service.

At 306, the business process identified for the order in 304 isexecuted. Executing the business process associated with the order mayinclude orchestrating the series of steps associated with the businessprocess identified in step 304. For example, executing a businessprocess related to provisioning physical resources for the order mayinclude sending a request to SDI module 206 to allocate resources andconfigure those resources needed to fulfill the subscription order.

At 308, a notification is sent to the customer regarding the status ofthe provisioned order. Additional description related to performingsteps 302, 304, 306 and 308 is provided in detail in FIG. 3B.

FIG. 3B depicts a simplified high level diagram of one or moresub-modules in the TAS module in the cloud infrastructure system, inaccordance with an embodiment of the present invention. In oneembodiment, the modules depicted in FIG. 3B perform the processingdescribed in steps 302-308 discussed in FIG. 3A. In the illustratedembodiment, TAS module 204 comprises an order processing module 310, abusiness process identifier 312, a business process executor 316, anoverage framework 322, a workflow identification module 324, and abundled subscription generator module 326. These modules may beimplemented in hardware, or software, or combinations thereof. Thevarious modules of the TAS module depicted in FIG. 3B are meant forillustrative purposes only and are not intended to limit the scope ofembodiments of the present invention. Alternative embodiments mayinclude more or fewer modules than those shown in FIG. 3B.

In one embodiment, order processing module 310 receives an order from acustomer from one or more input sources 321. For example, orderprocessing module 310 may directly receive an order via cloud UI 212 orstore UI 210, in one embodiment. Alternatively, order processing module310 may receive an order from order management module 214 or orderdatabase 224. Order processing module 310 then processes the order. Incertain embodiments, processing the order includes generating a customerrecord which includes information about the order such as a servicetype, a service level, a customer level, the type of resources, theamount of the resources to be allocated to the service instance and atime period during which the service is desired. As part of theprocessing, order processing module 310 also determines whether theorder is a valid order. This includes ensuring that the customer doesnot already have subscriptions with the same name or that the customeris not attempting to create multiple subscriptions of the same type inthe same identity domain for subscription types where this is disallowed(such as, in the case of a fusion CRM service).

Order processing module 310 may also perform additional processing onthe order. Processing may include tracking the status of an order foreach order that is being processed by cloud infrastructure system 100.In one embodiment, order processing module 310 may process each order toidentify a number of states pertaining to the order. In one example, thedifferent states of an order may be an initialized state, a provisionedstate, an active state, an administration required state, an errorstate, and the like. An initialized state refers to the state of a neworder; a provisioned state refers to the state of an order once theservices and resources for the order have been provisioned. An order isin an active state when the order has been processed by TAS module 204and a notification to that effect has been delivered to the customer. Anorder is in an administration required state when intervention by anadministrator is needed to resolve the issue. The order is in an errorstate when the order cannot be processed. In addition to maintaining theorder progress status, order processing module 310 also maintainsdetailed information about any failures encountered during processexecution. In other embodiments, and as will be discussed in detailbelow, the additional processing performed by order processing module310 may also include changing the service level for a service in thesubscription, changing the services included in the subscription,extending the time period of the subscription, and canceling thesubscription or specifying different service levels for different timeperiods in the subscription.

After an order has been processed by order processing module 310,business logic is applied to determine whether the order should proceedto provisioning. In one embodiment, as part of orchestrating the order,business process identifier 312 receives the processed order from orderprocessing module 310 and applies business logic to identify aparticular business process to use for the order being processed. In oneembodiment, business process identifier 312 may utilize informationstored in a service catalog 314 to determine the particular businessprocess to be used for the order. In one embodiment, and as discussed inFIG. 3A, multiple business processes may be identified for an order andeach business process identifies a series of steps for processingvarious aspects of the order. In another embodiment, and as discussedabove, different business processes may be defined for different typesof services, or combinations of services such as a CRM service or adatabase service. In one embodiment, service catalog 314 may storeinformation mapping an order to a particular type of business process.Business process identifier 312 may use this information to identify aspecific business process for the order being processed.

Once a business process has been identified, business process identifier312 communicates the particular business process to be executed tobusiness process executor 316. Business process executor 316 thenexecutes steps of the identified business process by operating inconjunction with one or more modules in the cloud infrastructure system100. In some embodiments, business process executor 316 acts as anorchestrator for performing the steps associated with a businessprocess. For example, the business process executor may interact withorder processing module 310 to execute steps in a business process thatidentifies workflows related to the order, determines the overage ofservices in the order or identifies service components related to theorder.

In one example, business process executor 316 interacts with SDI module206 to execute steps in a business process for allocating andprovisioning resources for services requested in the subscription order.In this example, for each step in the business process, business processexecutor 316 may send a request to SDI component 206 to allocateresources and configure resources needed to fulfill the particular step.SDI component 206 is responsible for the actual allocation of theresources. Once all the steps of the business processes of an order havebeen executed, business process executor 316 may send a notification tothe customer of the processed order by utilizing the services ofservices component 202. The notification may include sending an emailnotification to the customer with details of the processed order. Theemail notification may also include deployment information related tothe order to enable the customer to access the subscribed services.

In certain embodiments, TAS module 204 may provide one or more TASApplication Programming Interfaces (APIs) 318 that enable TAS module 204to interact with other modules in cloud infrastructure system 100 andfor other modules to interact with TAS module 204. For example, the TASAPIs may include a system provisioning API that interacts with SDImodule 206 via an asynchronous Simple Object Access Protocol (SOAP)based web services call to provision resources for the customer'ssubscription order. In one embodiment, TAS module 204 may also utilizethe system provisioning API to accomplish system and service instancecreation and deletion, switch a service instance to an increased servicelevel, and associate service instances. An example of this is theassociation of a Java service instance to a fusion applications serviceinstance to allow secure web service communications. The TAS APIs mayalso include a notification API that interacts with the services module202 to notify the customer of a processed order. In certain embodiments,the TAS module 204 also periodically propagates subscriptioninformation, outages, and notifications (e.g. planned downtime) toservices component 202.

In certain embodiments, TAS module 204 periodically receives usagestatistics for each of the provisioned services such as the amount ofstorage used, the amount data transferred, the number of users, and theamount of system up time and system down time from EM module 208.Overage framework 322 utilizes the usage statistics to determine whetherover use of a service has occurred, and if so, to determine how much tobill for the overage, and provides this information to order managementmodule 214.

In certain embodiments, TAS module 204 includes an order workflowidentification module 324 that is configured to identify one or moreworkflows associated with processing a customer's subscription order. Incertain embodiments, TAS module 204 may include a subscription ordergeneration framework 326 for generating subscription orders for acustomer when the customer places a subscription order for one or moreservices offered by the cloud infrastructure system 100. In oneembodiment, a subscription order includes one or more service componentsresponsible for providing the services requested by a customer in thesubscription order.

Additionally, TAS module 204 may also interact with one or moreadditional databases such as a Tenant Information System (TIS) database320 to enable the provisioning of resources for one or more servicessubscribed by the customer while taking into consideration historicalinformation, if any, available for the customer. TIS database 320 mayinclude historical order information and historical usage informationpertaining to orders subscribed by the customer.

TAS module 204 may be deployed using different deployment models. Incertain embodiments, the deployment includes a central component thatinterfaces with one or more distributed components. The distributedcomponents may, for example, be deployed as various data centers andaccordingly may also be referred to as data center components. Thecentral component includes capabilities to process orders andco-ordinate services in cloud infrastructure system 100, while the datacenter components provide capabilities for provisioning and operatingthe runtime system that provides the resources for the subscribedservices.

FIG. 4 depicts an exemplary distributed deployment of the TAS module,according to an embodiment of the present invention. In the embodimentdepicted in FIG. 4, the distributed deployment of TAS module 204includes a TAS central component 400 and one or more TAS Data Centers(DCs) components 402, 404 and 406. These components may be implementedin hardware, or software, or combinations thereof.

In one embodiment, the responsibilities of TAS central component 400include, without limitation, to provide a centralized component forreceiving customer orders, performing order-related business operationssuch as creating a new subscription, changing the service level for aservice in the subscription, changing the services included in thesubscription, and extending the time period of the subscription, orcanceling the subscription. The responsibilities of TAS centralcomponent 400 may also include maintaining and serving subscription dataneeded by cloud infrastructure system 100 and interfacing with ordermanagement module 214, support UI 216, cloud UI 212 and store UI 210 tohandle all the back-office interactions.

In one embodiment, the responsibilities of TAS DCs 402, 404 and 406include, without limitation, performing runtime operations fororchestrating the provisioning the resources for one or more servicessubscribed by the customer. TAS DCs 402, 404 and 406 also includecapabilities to perform operations such as locking, unlocking, enabling,or disabling a subscription order, collecting metrics related to theorder, determining the status of the order, and sending notificationevents related to the order.

In an exemplary operation of the distributed TAS system shown in FIG. 4,TAS central component 400 initially receives an order from a customervia cloud UI 212, store UI 210, via order management system 214, or viaorder database 224. In one embodiment, the customer represents a buyerwho has financial information and the authority to order and/or change asubscription. In one embodiment, the order information includesinformation identifying the customer, the type of services that thecustomer wishes to subscribe to, and an account administrator who willbe responsible for handling the request. In certain embodiments, theaccount administrator may be nominated by the customer when the customerplaces an order for a subscription to one or more services offered bycloud infrastructure system 100. Based on the order information, the TAScentral component 400 identifies the data region of the world such asAmericas, EMEA, or Asia Pacific in which the order originates and theparticular TAS DCs (for e.g., 402, 404 or 406) that will be deployed forprovisioning the order. In one embodiment, the particular TAS DC (fore.g., from among DCs 402, 404 or 406) that will be deployed forprovisioning the order is determined based on the geographical dataregion in which the request originated.

TAS central component 400 then sends the order request to the particularTAS DC in which to provision services for the order request. In oneembodiment, TAS DCs 402, 404 or 406 identify a service administrator andan identity domain administrator responsible for processing the orderrequest at the particular TAS DC. The service administrator and theidentity administrator may be nominated by the account administratoridentified in the subscription order. TAS DCs 402, 404 or 406communicate with SDI module 204 to orchestrate the provisioning ofphysical resources for the order. SDI component 204 in respective TASDCs 402, 404 or 406 allocates resources and configures those resourcesneeded to fulfill the subscription order.

In certain embodiments, TAS DCs, 402, 404 or 406 identify an identitydomain associated with the subscription. SDI component 206 may providethe identity domain information to IDM component 200 (shown in FIG. 2)for identifying an existing identity domain or creating a new identitydomain. Once the order is provisioned by the SDI module at respectiveTAS DCs, 402, 404 or 406, TAS central component 400 may placeinformation regarding the provisioned resources in a support system, viasupport UI 216. Information may include, for example, displayingresource metrics related to the services and usage statistics of theservices.

Once in operation, at each data center, EM module 208 to periodicallycollects usage statistics for each of the provisioned servicesprovisioned at that data center, such as the amount of storage used, theamount data transferred, the number of users, and the amount of systemup time and system down time. These statistics are provided to the TASDC that is local to EM module 208 (i.e., at the same data center). In anembodiment, the TAS DCs may use the usage statistics to determinewhether overuse of a service has occurred, and if so, to determine howmuch to bill for the overage, and provide the billing information toorder management system 214.

FIG. 5 is a simplified block diagram illustrating the interactions ofthe SDI module with one or more modules in the cloud infrastructuresystem, in accordance with an embodiment of the present invention. Inone embodiment, SDI module 206 interacts with TAS module 204 toprovision resources for services in a subscription order received by TASmodule 204. In certain embodiments, one or more of the modulesillustrated in FIG. 5 may be modules within cloud infrastructure system100. In other embodiments, one or more of the modules that interact withSDI module 206 may be outside cloud infrastructure system 100. Inaddition, alternative embodiments may have more or less modules thanthose shown in FIG. 5. These modules may be implemented in hardware, orsoftware, or combinations thereof.

In one embodiment, the modules in SDI module 206 may include one or moremodules in SaaS platform 102 and PaaS platform 104 in cloudinfrastructure system 100. In order to perform provisioning of resourcesfor various services, SDI module 206 may interact with various othermodules, each customized to help with provisioning resources for aparticular type of service. For example, as illustrated in FIG. 5, SDImodule 206 may interact with a Java service provisioning control module500 to provision Java cloud services. In one embodiment, Java serviceprovisioning control component 500 may deploy a Java Cloud Service (JCS)assembly specified by SDI module 206 that includes a set of tasks to beperformed to provision Java cloud services. Infrastructure resources 106then determines the resources needed to provision the Java cloudservices.

As other examples, SDI module 206 may interact with one or more modulessuch as a Virtual Assembly Builder (VAB) module 502, an ApplicationExpress (APEX) deployer module 504, a Virtual Machine (VM) module 506,an IDM module 200, and a database machine module 118. VAB module 502includes capabilities to configure and provision complete multi-tierapplication environments. In one embodiment, VAB module 502 deploys aMiddleware (MW) service assembly specified by SDI module 206 toprovision a MW service in cloud infrastructure system 100 using theservices provided by VM module 506. APEX deployer module 504 includescapabilities to configure and provision database services. In oneembodiment, APEX deployer module 504 deploys a database service assemblyspecified by SDI module 206 to provision a database service in cloudinfrastructure system 100 using the resources provided by infrastructureresources 106. SDI module 206 interacts with IDM module 200 to provideidentity services such as access management across multiple applicationsin cloud infrastructure system 100.

FIG. 6 depicts a simplified high level diagram of sub-modules of the SDImodule according to an embodiment of the present invention. In theembodiment depicted in FIG. 6, SDI module 206 includes a SDI-WebServices (WS) module 600, an SDI request controller module 602, an SDItask manager module 604, an SDI monitoring module 606, an SDI dataaccess module 608, an SDI common library module 610, and an SDIconnector module 612. These modules may be implemented in hardware, orsoftware, or combinations thereof SDI module 206 depicted in FIG. 6 andits various modules are meant for illustrative purposes only and are notintended to limit the scope of embodiments of the present invention.Alternative embodiments may have more or less modules than those shownin FIG. 6. These modules and their functions are described in detailbelow.

SDI-WS module 600 includes capabilities for receiving a step in thebusiness associated with an order from business process executor 316 ofTAS component 204. In one embodiment, SDI-WS module 600 parses each stepof the business process and converts the step into an internalrepresentation used by SDI module 206. In one embodiment, each step ofthe business process associated with the order arrives through a webservice processing layer (for example, via System Provisioning APIdiscussed in FIG. 3B) in the form of a SOAP request to SDI-WS module600.

SDI request controller module 602 is the internal request processingengine in SDI module 206 and includes capabilities for performingasynchronous request processing, concurrent request processing,concurrent task processing, fault tolerant and recovery and plug-insupport related to the order requests. In one embodiment, SDI requestcontroller module 602 accepts each step of the business processassociated with the order from SDI-WS module 600 and submits the step toSDI task manager module 604.

SDI task manager module 604 translates each step specified in thebusiness process into a series of tasks for provisioning the particularstep. Once the set of tasks for a specific step have been provisioned,SDI task manager module 604 responds to business process executor 316 inTAS module 204 with operation results that includes an order payloadwith details of the resources provisioned to fulfill the particularstep. SDI task manager module 604 repeats this process until all thesteps of the particular business process associated with the order arecomplete.

In certain embodiments, SDI task manager module 604 translates each stepspecified in the business process into a series of tasks by utilizingthe services of SDI connector module 612. SDI connector module 612includes one or more connectors for handling the deployment of tasksspecified by SDI task manager module 604 to provision one or moreservices related to the order request. In certain embodiments, one ormore of the connectors may handle tasks that are specific to aparticular service type while other connectors may handle tasks that arecommon across different service types. In one embodiment, SDI connectormodule 612 includes a set of connectors (wrapper APIs) that interfacewith one or more of the external modules (shown in FIG. 5) in cloudinfrastructure system 100 to provision the services and resourcesrelated to the order request. For example, Application Express (APEX)connector 614 interfaces with APEX deployer module 504 to provisiondatabase services. Web Center Connector 616 (WCC) interfaces with a webcenter module in cloud infrastructure system 100 to provision webservices. The web center module is a user engagement platform andincludes capabilities for delivering connectivity between people andinformation in cloud infrastructure system 100.

In certain embodiments, Middleware Applications (MA) connector 618interfaces with VAB module 502 in cloud infrastructure system 100 toprovision middleware application services. NUVIAQ connector 620interfaces with VAB module 502 to provision Java services. IDM connector622 interfaces with IDM module 200 to provide identity and accessmanagement for users subscribing to services and resources in cloudinfrastructure system 100. Virtual Assembly Builder (VAB) connector 624interfaces with VAB module 502 in cloud infrastructure system 100 toconfigure and provision complete multi-tier application environments.Plug-in connector 626 interfaces with EM module 208 to manage andmonitor the components in cloud infrastructure system 100. HTTP serverconnector 628 interfaces with one or more web servers in the PaaSplatform to provide connection services to users in cloud infrastructuresystem 100.

SDI monitoring module 606 in SDI module 206 provides an inboundinterface for receiving Java Management Extensions (JMX) requests. SDImonitoring module 606 also provides tools for managing and monitoringapplications, system objects and devices in cloud infrastructure system100. SDI-data access module 608 provides an inbound interface forreceiving Java Database Connectivity (JDBC) requests. SDI-data accessmodule 608 supports data access and provides object relational mapping,java transaction API services, data access objects, and connectionpooling in cloud infrastructure system 100. The SDI-common librarymodule 610 provides configuration support for the modules in SDI module206.

The embodiment of FIG. 6 discussed above describes modules in the SDImodule according to an embodiment of the present invention. FIG. 7Adepicts a simplified flowchart 700 depicting processing that may beperformed by the modules of the SDI module in the cloud infrastructuresystem, in accordance with an embodiment of the present invention. Theprocessing depicted in FIG. 7A may be implemented in software (e.g.,code, instructions, program) executed by one or more processors,hardware, or combinations thereof. The software may be stored in memory(e.g., on a memory device, on a non-transitory computer-readable storagemedium). The particular series of processing steps depicted in FIG. 7Ais not intended to be limiting. Other sequences of steps may also beperformed according to alternative embodiments. For example, alternativeembodiments of the present invention may perform the steps outlinedabove in a different order. Moreover, the individual steps illustratedin FIG. 7A may include multiple sub-steps that may be performed invarious sequences as appropriate to the individual step. Furthermore,additional steps may be added or removed depending on the particularapplications. One of ordinary skill in the art would recognize manyvariations, modifications, and alternatives. In one embodiment, theprocessing depicted in FIG. 7A may be performed by one or more modulesin the SDI module 206 discussed in detail in FIG. 6.

At 702, a business process associated with a subscription order isreceived. In one embodiment, SDI-WS module 600 in SDI module 206receives one or more steps in the business process associated with thesubscription order from business process executor 316. At 704, each stepin the business process is translated into a series of tasks forprovisioning resources for the subscription order. In one embodiment,SDI task manager module 604 in SDI module 206 translates each stepspecified in the business process into a series of tasks by utilizingthe services of SDI connector module 612. At 706, the subscription orderis provisioned based on the series of tasks. In one embodiment, and asdiscussed in FIG. 6, SDI connector module 612 includes one or moreconnectors for handling the deployment of tasks specified by SDI taskmanager module 604 to provision resources for the services in thesubscription order.

As described above with respect to FIG. 6, SDI task manager module 604translates each step specified in a business process into a series oftasks by utilizing the services of SDI connector module 612, which mayinclude one or more connectors for handling the deployment of tasksspecified by SDI task manager module 604 to provision one or moreservices related to the order request. One or more of the connectors mayhandle tasks that are specific to a particular service type while otherconnectors may handle tasks that are common across different servicetypes. In one embodiment, SDI connector module 612 includes a set ofconnectors (wrapper APIs) that interface with one or more of theexternal modules (shown in FIG. 5) in cloud infrastructure system 100 toprovision the services and resources related to the order request. Forexample, a NUVIAQ connector 620 interfaces with VAB module 502 toprovision Java services.

FIG. 7B depicts a simplified block diagram showing the high-levelarchitecture of a Nuviaq system 710 and its relationships with othercloud infrastructure components according to an embodiment of thepresent invention. It should be appreciated that Nuviaq system 710depicted in FIG. 7B may have other components than those depicted inFIG. 7B. Further, the embodiment shown in FIG. 7B is only one example ofa cloud infrastructure system that may incorporate an embodiment of theinvention. In some other embodiments, Nuviaq system 710 may have more orfewer components than shown in FIG. 7B, may combine two or morecomponents, or may have a different configuration or arrangement ofcomponents.

In certain embodiments, Nuviaq system 710 may be configured to provide aruntime engine for orchestrating PaaS operations. Nuviaq system 710 mayprovide a web service API to facilitate integration with other productsand services. Nuviaq system 710 also provides support for complexworkflows in system provisioning, application deployment and associatedlifecycle operations and integrates with management and monitoringsolutions.

In the embodiment depicted in FIG. 7B, Nuviaq system 710 comprises aNuviaq proxy 712, a Nuviaq manager 714, and a Nuviaq database 716. Incertain embodiments, Nuviaq manager 714 provides an entry point intoNuviaq system 710, providing secure access to PaaS operations via theweb service API. Internally, it tracks system state in the database andcontrols job execution on the workflow engine. In a public cloud, Nuviaqmanager 714 may be accessed by the Tenant Provisioning system (SDI 206)and the Tenant Console, to drive provisioning and deployment operationsrespectively.

In one embodiment, Nuviaq manager 714 executes jobs asynchronously viaan internal workflow engine. A job may be a sequence of actions specificto a given PaaS workflow. Actions may be performed in order, withfailure in any step resulting in failure of the overall job. Manyworkflow actions delegate to external systems relevant to the workflow,such as the EM command line interface (cli). In one implementation,Nuviaq manager 714 application may be hosted in a 2-node WebLogiccluster with associated HTTP server (e.g., Oracle HTTP Server or OHS)instance, running inside a firewall.

In certain embodiments, Nuviaq proxy 712 is the public access point tothe Nuviaq API. In one embodiment, only Public API may be exposed here.Requests received by proxy 712 may be forwarded to Nuviaq manager 714.In one embodiment, Nuviaq proxy 712 runs outside the firewall, whereasmanager 714 runs within the firewall. In one implementation, Nuviaqproxy 712 application runs on a WebLogic cluster running outside thefirewall.

In certain embodiments, Nuviaq database 716 tracks various domainentities such as, without limitation, platform instance, deploymentplan, application, WebLogic domain, jobs, alerts, and the like. Primarykeys may be aligned with the Service Database where appropriate.

In one embodiment, Platform Instance 718 may contain all resourcesrequired for a WebLogic service for a given tenant.

Nuviaq system 710 may rely on additional systems of cloud infrastructuresystem 100 to carry out the workflows used the WebLogic cloud service.These dependencies may include dependencies on SDI 206, IDM 200, a virusscan system, a service database, CRM instances, and the like. Forexample, Nuviaq system 710 may depend upon functions performed by anAssembly Deployer in SDI 206. In one embodiment, the Assembly Deployeris a system to manage interactions with OVAB (Oracle Virtual AssemblyBuilder) and OVM (Oracle Virtual Machine). Capabilities of the AssemblyDeployer used by Nuviaq system 710 may include, without limitation,functions for deploying an assembly, un-deploying an assembly,describing assembly deployment, scaling appliance, and the like. In oneimplementation, Nuviaq system 710 accesses the Assembly Deployer via aweb service API.

In certain embodiments, security policies may require certain artifactsto be scanned for viruses before being deployed to an application. Cloudinfrastructure system 100 may provide a virus scan system for thispurpose that provides scanning as a service for multiple components ofthe public cloud.

In certain embodiments, a public cloud infrastructure may maintain aService Database containing information about tenants (e.g., customers)and their service subscriptions. Nuviaq workflows may access to thisdata in order to properly configure a WebLogic service as a client toother services that the tenant also subscribes to.

Nuviaq system 710 may depend on IDM 200 for its security integration. Incertain embodiments, Java Service instances can be associated with a CRMinstance. The association allows user applications deployed to theirJava Service instance to access a CRM instance though Web Service calls.

Various entities may use services provided by Nuviaq system 710. Theseclients of Nuviaq system 710 may include: a Tenant Console, which is anmanagement server (e.g., Oracle Management Server) based user interfacethat customers may access to manage their applications on their platforminstances; several IDEs such as Oracle IDEs (JDeveloper, NetBeans, andOEPE) have been extended to offer access to application lifecyclemanagement operations; one or more Command Line Interfaces (CLIs) thatare available to access lifecycle operations on the platform instances.

Provisioning use case for Nuviaq system 710—A Provision PlatformInstance use case is realized via the Create Platform Instance operationof the Nuviaq API. In the context of cloud infrastructure system 100, aservice instance with respect to the Nuviaq system corresponds to aNuviaq platform instance. A platform instance is assigned a uniqueidentifier is used on all subsequent operations related to thisinstance. A Platform Deployment descriptor provided to the CreatePlatform Instance action allows for properties to be set that modify theconfiguration of the platform instance to meet the subscriptionrequirements of the tenant. These properties may include for example:

-   Property#1: oracle.cloud.service.weblogic.size    -   Values: BASIC, STANDARD, ENTERPRISE    -   Description: Specifies the subscription type. This impacts the        number of servers, database limits and quality of service        settings.-   Property#2: oracle.cloud.service.weblogic.trial    -   Values: TRUE, FALSE    -   Description: Indicates whether or not this is a trial        subscription.-   Property#3: oracle.cloud.service.weblogic.crm    -   Values: CRM Service ID    -   Description: Identifies a CRM service to be associated with this        WebLogic service instance.

FIG. 7C depicts an example sequence diagram illustrating steps of aprovisioning process using a Nuviaq system according to an embodiment ofthe present invention. The sequence diagram depicted in FIG. 7C is onlyan example and is not intended to be limiting.

Install/Update Application use case—The Install Application operationdeploys an application to a running WebLogic Server after validatingthat the application archive meets the security requirements of thePublic Cloud. In one embodiment, the Application Deployment descriptorprovided to the Install Application action allows for properties to beset that modify the configuration of the application to meet thesubscription requirements of the tenant. These properties may includefor example:

-   Property: oracle.cloud.service.weblogic.state-   Values: RUNNING, STOPPED-   Description: Specifies the initial state of the application after    deployment.

FIG. 7D depicts an example sequence diagram illustrating steps of adeployment process using a Nuviaq system according to an embodiment ofthe present invention. The sequence diagram depicted in FIG. 7D is onlyan example and is not intended to be limiting.

Referring back to FIG. 2, in certain embodiments, TAS 204 and SDI 206working in cooperation are responsible for provisioning resources forone or more services ordered by a customer from a set of servicesoffered by cloud infrastructure system 100. For example, in oneembodiment, for provisioning a database service, the automatedprovisioning flow may be as follows for a paid subscription:

-   (1) Customer places an order for a paid subscription to a service    via Store UI 210.-   (2) TAS 204 receives the subscription order.-   (3) When services are available TAS 204 initiates provisioning by    using the services of SDI 206. TAS 204 may perform business process    orchestration, which will execute the relevant business process to    complete the provisioning aspect of the order. In one embodiment,    TAS 204 may use a BPEL (Business Process Execution Language) Process    Manager to orchestrate the steps involved in the provisioning and    handle the lifecycle operations.-   (4) In one embodiment, to provision a database service, SDI 206 may    call PLSQL APIs in the CLOUD_UI to associate a schema for the    requesting customer.-   (5) After successful association of a schema to the customer, SDI    signals TAS and TAS send a notification to the customer that the    database service is now available for use by the customer.-   (6) The customer may log into cloud infrastructure system 100 (e.g.,    using an URAL such as cloud.oracle.com) and activate the service.

In some embodiments, a customer may also be allowed to subscribe to aservice on a trial basis. For example, such a trial order may bereceived via cloud UI 212 (e.g., using cloud.oracle.com).

In certain embodiments, cloud infrastructure system 100 enablesunderlying hardware and service instances to be shared between customersor tenants. For example, the database service may be provisioned asshown in FIG. 7E in one embodiment. FIG. 7E depicts multiple Exadatacompute nodes 730 and 732, each providing a database instanceprovisioned for the database service. For example, compute node 730provides a database instance 734 for a database service. Each Exadatacompute node may have multiple database instances.

In certain embodiments, each database instance can comprise multipleschemas and the schemas may be associated with different customers ortenants. For example, in FIG. 7E, database instance 734 provides twoschemas 736 and 738, each with its own tables. Schema 736 may beassociated with a first customer or tenant subscribing to a databaseservice and schema 738 may be associated with a second customer ortenant subscribing to the database service. Each tenant gets acompletely isolated schema. Each schema acts like a container that canmanage database objects including tables, views, stored procedures,triggers, etc. for the associated tenant. Each schema may have onededicated tablespace, with each tablespace having one data file.

In this manner, a single database instance can provide database servicesto multiple tenants. This not only enables sharing of underlyinghardware resources but also enables sharing of service instance betweentenants.

In certain embodiments, such a multi-tenancy system is facilitated byIDM 200, which beneficially enables multiple separate customers, eachhaving their own separate identity domains, to use hardware and softwarethat is shared in the cloud. Consequently, there is no need for eachcustomer to have its own dedicated hardware or software resources, andin some cases resources that are not being used by some customers at aparticular moment can be used by other customers, thereby preventingthose resources from being wasted. For example, as depicted in FIG. 7E,a database instance can service multiple customers each with theirrespective identity domains. Although each such database serviceinstance can be a separate abstraction or view of a single physicalmulti-tenant database system that is shared among the many separateidentity domains, each such database service instance can have aseparate and potentially different schema than each other databaseservice instance has. Thus, the multi-tenant database system can storemappings between customer-specified database schemas and the identitydomains to which those database schemas pertain. The multi-tenantdatabase system can cause the database service instance for a particularidentity domain to use the schema that is mapped to that particularidentity domain.

The multi-tenancy can also be extended to other services such as theJava Service. For example, multiple customers can have a JAVA serviceinstance placed within their respective identity domains. Each suchidentity domain can have a JAVA virtual machine, which can be viewed asbeing a virtual “slice” of hardware. In one embodiment, a job-monitoringservice (e.g., Hudson) can be combined with a JAVA enterprise editionplatform (e.g., Oracle WebLogic) in the cloud to enable each separateidentity domain to have its own separate virtual “slice” of the JAVAenterprise edition platform. Such a job-monitoring service can, forexample, monitor the execution of repeated jobs, such as building asoftware project or jobs run by an operating system's time-based jobscheduler. Such repeated jobs can include the continuous building and/ortesting of software projects. Additionally or alternatively, suchrepeated jobs can include the monitoring of executions of operatingsystem-run jobs that are executed on machines that are remote from themachine on which the job-monitoring service executes.

In certain situations, processing a customer's subscription order incloud infrastructure system 100 may involve the storage of sensitiveinformation related to the customer's subscription order by one or morecomponents in the cloud infrastructure system. For example, sensitiveinformation stored by the components in cloud infrastructure system 100may include confidential customer information such as customer'sidentities, credit card information, contract details, informationrelated to a customer's access to resources provisioned to one or moreservices in the customer's subscription order and so on. In oneembodiment, cloud infrastructure system provides a framework forhandling the secure interaction between these components that wish totransfer information between each other during processing of acustomer's subscription order. In one embodiment, the components areassigned to various security zones. The assignment of a component to asecurity zone may be based upon the sensitivity of the data handled bythe components, the sensitivity of functions performed by the component,and the like.

FIG. 8A is a logical view of the assignment of security zones to variouscomponents in the cloud infrastructure system in accordance with oneembodiment of the present invention. As depicted in FIG. 8, varioussecurity zones may be assigned to one or more components of cloudinfrastructure system 100 such as an identity management zone 802, aphysical provisioning zone 804, an accounting zone 806, a tenant zone808 and a customer UI zone 810. In addition, a security level may beassociated with each security zone. In one embodiment, the securitylevels are selected from a high security level 812, a medium securitylevel 814, and a low security level 816.

In one embodiment, the assignment of a component to a security zone anda security level may be based upon the sensitivity of the data handledby the components, the sensitivity of functions performed by thecomponent, and the like. There may be multiple zones with the same levelof security. As an example, one or more components in order managementmodule 214 that perform back office functions such as billing andmaintaining confidential customer information may be assigned to asecurity zone with a high security level. Similarly, components in IDMmodule 200 that maintain identity information within the data centers ofcloud infrastructure system 100 and components in SDI module 206 thatprovision and control a customer's access to resources in cloudinfrastructure system 100 may be assigned to a security zone with a highsecurity level. Components that orchestrate the provisioning ofresources in cloud infrastructure system 100 and enable monitoring ofservices in the customer's subscription order in TAS module 204 and EMmodule 208 may be assigned to a security zone with a medium securitylevel. Components that provide a user interface to customers in cloud UI212, store UI 210 and support UI 216 may be assigned to a security zonewith a low security level.

The assignment of a component to a security zone with an associatedsecurity level may also be performed based on the distance of acomponent from the end user or customer. In one example, the closer acomponent is to the end user, the lower is the security level of thesecurity zone of the component. For example, the user interface relatedcomponents in cloud UI 212, store UI 210, and support UI 216, which aredirectly accessible by a user, are assigned to customer UI zone 810associated with a low security level. On the other hand, back-officeprocessing components in order management module 214 are assigned toaccounting zone 806 associated with a high security level 812.

In the example depicted in FIG. 8A a component in SDI module 206 isassigned to physical provisioning zone 804 associated with high securitylevel 812. A component in IDM module 200 is assigned to identitymanagement zone 802 associated with a high security level 812. Acomponent in order management module 214 is assigned to accounting zone806 associated with a high security level 812. Components in TAS module204, EM module 208, and support system 217 are assigned to tenant zone808 associated with a medium security level 814. Components in cloud UI212, store UI 210, and support UI 216 are assigned to customer UI zone810 associated with a low security level 816. In one embodiment, theassignment of a component to a particular security zone and particularsecurity level may be performed by an administrator of cloudinfrastructure system 100. In certain embodiments, information may bestored by cloud infrastructure system 100 mapping each component to itsassociated security zone and security level.

It is to be appreciated that the security zones and security levelsdiscussed above are not intended to limit the scope of the presentinvention but are merely discussed to provide an example. Additionalexemplary security zones and security levels may be defined forcomponents of cloud infrastructure system 100, in other embodiments. Aparticular zone may comprise zero or more components. One of ordinaryskill in the art would recognize many variations, modifications, andalternatives.

In certain embodiments of the present invention, the ability of twocomponents to interact with each other, including the ability of the twocomponents to exchange data with one another is determined based on thesecurity zones to which the components are assigned and the securitylevels associated with the zones. The security zones and theirassociated security levels thus control the transfer of informationbetween components in cloud infrastructure system 100. A securityzone-based security infrastructure 900 is defined that facilitates theinteraction between one or more components in cloud infrastructuresystem 100 in a secure manner.

In one embodiment, security zone-based security infrastructure 900defines a set of one or more rules for facilitating the interactionbetween one or more components that wish to transfer information betweeneach other, based on the security zones and the security levels.

FIG. 8B illustrates a security zone-based security infrastructure 900according to an embodiment of the present invention. In one embodiment,security infrastructure system 900 is used to control interactionsbetween one or more components in cloud infrastructure system 100. Asillustrated in FIG. 8B, in one embodiment, security infrastructuresystem 900 includes a security layer component 906, and information thatis used by security layer component 906. In one embodiment, theinformation used by security layer component 906 comprises component tosecurity zone mapping information 908, security zone to security levelmapping information 910, and rules information 912. Information 908,910, and 912 may be stored in various forms. For example, in oneembodiment, component to security zone information 908 may be stored asa table with one column of the table identifying the components and asecond column of the table identifying a security zone to which eachcomponent is assigned. Likewise, in one embodiment, security zone tosecurity level information 910 may be stored as a table with one columnof the table identifying security zones and a second column of the tableidentifying a security level for each security zone.

In one embodiment, security layer component 906 may be provided as aseparate component in cloud infrastructure system 100. In such anembodiment, an interaction request from source component 902 to targetcomponent 904 may be intercepted by security layer component 906.Security layer component 906 may then process the request and based uponthe results of the processing, enable the transfer of informationbetween the source component and the target component.

In another embodiment, security layer component 906 may be part of eachcomponent in cloud infrastructure system 100. In such an embodiment, aninteraction request originating from a source component 902 may bepassed to security layer component 906 within the components. Thesecurity layer component within the components may then process therequest and based upon the results of the processing, enable thetransfer of information between the source component and the targetcomponent.

The security-related processing performed by security layer component906 may be explained using the following example. Consider a situationwhere source component 902 wishes to transfer information to the targetcomponent 904 while processing a customer's subscription order in cloudinfrastructure system 100. Source component 902 may originate a requestto transfer information to target component 904. Security layercomponent 906 is configured to receive or intercept this request. Fromthe request, security layer component 906 determines the identities ofthe source component and the target component. Using component tosecurity zone information 908, security layer component 906 determines asecurity zone (referred to as the source security zone) to which sourcecomponent 902 belongs to and a security zone (referred to as the targetsecurity zone) to which target component 904 belongs to. Security layercomponent 906 then uses security zone to security level mappinginformation 910 to determine a security level (referred to as sourcesecurity level) for the source security zone and a security level(referred to as target security level) for the target security zone.

Once the source security level and target security level have beenidentified, security layer component 906 consults security rulesinformation 912 to control interactions between the source component andthe target component. In certain embodiments, security rules information912 may specify various rules that govern the transfer of informationbetween the source component and the target component. In oneembodiment, and as will be discussed in detail below, the rules specifywhen information is permitted to be pushed from one security level toanother and when information is permitted to be pulled by one securitylevel from another security level. Accordingly, rules may be specifiedbased on a push-pull communication model for one or more componentswithin cloud infrastructure system 100. The push-pull rules are intendedto protect the transfer of information from a less secure zone to a moresecure zone. A component in a higher security zone pushes information toa component in a lower security zone and pulls information from acomponent in a lower security zone. A component in a lower security zonemay not have direct read or write access to the data managed by acomponent in a higher security zone. Components within the same securityzone may have read or write access with respect to each other.

In one embodiment, the set of rules that govern the transfer ofinformation between the source component and the target component are asfollows:

-   -   If the target component is in a security zone with a lower        security level than the security level of the security zone of        the source component or if the target component is in a security        zone with the same security level as the security level of the        security zone of the source component, then the source component        pushes the information to the target component.    -   If the target component is in a security zone with a security        level that is higher than the security level of the security        zone of the source component, then the source component        publishes the information, such as, by writing the information        to an output queue of the source component, and the target        component may then pull this information from the output queue.

In certain embodiments, components within the cloud infrastructuresystem have read/write access with respect to each other based on theirsecurity levels. These read/write operations may be performed viaappropriate APIs. In one embodiment, if the source component wants totransfer information to the target component and the security level ofthe source component is higher than the security level of the targetcomponent, it pushes information to the target component. In such asituation, the source component invokes a synchronous write API of thetarget component. As an example, source component 902 may invoke a webservice API or a PL/SQL API of target component 904 to push informationto target component 904. As another example, source component 902 maypush the information to target component 904 in an asynchronous mannersuch as by publishing the information to a queue in target component904.

In another embodiment, if the source component needs to get informationfrom the target component and the security level of the target componentis lower than the security level of the source component or the securitylevel of the target component is the same as the security level of thesource component, the source component pulls the information from thetarget component by calling a synchronous read API of the targetcomponent. In one example, the source component may invoke a web serviceor a PL/SQL API of the target component. If the security level of thetarget component is higher than the security level of the sourcecomponent, the source component publishes its request for informationsuch as in an output queue of the source component and the targetcomponent pulls this request published by the source component and thenpushes the requested information to the source component.

As an example, consider an exemplary interaction between a component inorder management module 214 and a component in TAS module 204 whileprocessing a customer's subscription order in cloud infrastructuresystem 100. The component in order management module 214 is assigned toa security zone that is in a high security level whereas the componentin TAS module 204 is assigned to a security zone that is in a mediumsecurity level. This is because all interactions between a component inorder management module 214 and a component in TAS module 204 arecontrolled by the component in order management module 214. Thecomponent in order management module 214 creates an order and pushes theorder into the component in TAS module 204. Information flowing from thecomponent in TAS module 204 to the component in order management module214 is stored in a queue on the component in TAS module 204 and it isthen pulled from this queue by the component in order management module214.

In certain embodiments, when a new component is introduced into cloudinfrastructure system 100, security infrastructure 900 may also allow anadministrator of cloud infrastructure system 100 to assign one of theexisting security zones to the component or to create a new securityzone with an associated security level for the component.

Security infrastructure 900 may also allow an administrator of cloudinfrastructure system 100 to change associations between components andsecurity zones and also the mappings between security zones and securitylevels. For example, when the feature set of a component changes, it ispossible that the administrator may move the component to a differentsecurity zone. In this manner, an administrator of cloud infrastructuresystem 100 is provided complete control and flexibility on the flow ofinformation between components of cloud infrastructure system 100.

FIG. 9 depicts a simplified flowchart 914 depicting processing that maybe performed by security infrastructure 900 in cloud infrastructuresystem 100, in accordance with an embodiment of the present invention.The processing depicted in FIG. 9 may be implemented in software (e.g.,code, instructions, program) executed by one or more processors,hardware, or combinations thereof. The software may be stored in memory(e.g., on a memory device, on a non-transitory computer-readable storagemedium). The particular series of processing steps depicted in FIG. 9 isnot intended to be limiting. Other sequences of steps may also beperformed according to alternative embodiments. For example, alternativeembodiments of the present invention may perform the steps outlinedabove in a different order. Moreover, the individual steps illustratedin FIG. 9 may include multiple sub-steps that may be performed invarious sequences as appropriate to the individual step. Furthermore,additional steps may be added or removed depending on the particularapplications. One of ordinary skill in the art would recognize manyvariations, modifications, and alternatives. In one embodiment, theprocessing depicted in FIG. 9 may be performed by one or more componentsin the security infrastructure 900 discussed in detail in FIG. 8A.

At 916, a request to transfer information between a first component(also referred to as a source component) and a second component (alsoreferred to as a target component) in cloud infrastructure system 100 isreceived.

At 918, a first security zone for the first component and a secondsecurity zone for the second component are determined. In oneembodiment, the security zones that may be assigned to the firstcomponent and the second component may include an identity managementzone, a physical provisioning zone, an accounting zone, a tenant zoneand a customer UI zone.

At 920, a first security level associated with the first security zoneand a second security level associated with the second security zone aredetermined. In one embodiment, the security levels associated with asecurity zone may include a high security level, a medium security levelor a low security level.

At 922, the transfer of information between the first component and thesecond component is determined based upon the first security level, thesecond security level, and security rules information. In oneembodiment, the security rules information specifies one or more rulesrelated to the transfer of information between the first component andthe second component. In one embodiment, and as discussed in FIG. 8, ifthe source component wants to transfer information to the targetcomponent and the security level of the source component is higher thanthe security level of the target component, it pushes information to thetarget component. In such a situation, the source component invokes asynchronous write API of the target component or publishes theinformation to a queue in the target component. On the hand, if thetarget component is in a security zone with a security level that ishigher than the security level of the security zone of the sourcecomponent, then the source component publishes the information, such as,by writing the information to an output queue of the source component,and the target component may then pull this information from the outputqueue.

In another embodiment, if the source component needs to get informationfrom the target component and the security level of the target componentis lower than the security level of the source component or the securitylevel of the target component is the same as the security level of thesource component, the source component pulls the information from thetarget component by calling a synchronous read API of the targetcomponent. On the other hand, if the security level of the targetcomponent is higher than the security level of the source component, thesource component publishes its request for information such as in anoutput queue of the source component and the target component pulls thisrequest published by the source component and then pushes the requestedinformation to the source component.

FIG. 10 is a simplified block diagram of a computing system 1000 thatmay be used in accordance with embodiments of the present invention. Forexample, cloud infrastructure system 100 may comprise one or morecomputing devices. System 1000 depicted in FIG. 10 may be an example ofone such computing device. Computer system 1000 is shown comprisinghardware elements that may be electrically coupled via a bus 1024. Thehardware elements may include one or more central processing units(CPUs) 1002, one or more input devices 1004 (e.g., a mouse, a keyboard,etc.), and one or more output devices 1006 (e.g., a display device, aprinter, etc.). The CPUs may include single or multicore CPUs. Computersystem 1000 may also include one or more storage devices 1008. By way ofexample, the storage device(s) 1008 may include devices such as diskdrives, optical storage devices, and solid-state storage devices such asa random access memory (RAM) and/or a read-only memory (ROM), which canbe programmable, flash-updateable and/or the like.

Computer system 1000 may additionally include a computer-readablestorage media reader 1012, a communications subsystem 1014 (e.g., amodem, a network card (wireless or wired), an infra-red communicationdevice, etc.), and working memory 1018, which may include RAM and ROMdevices as described above. In some embodiments, computer system 1900may also include a processing acceleration unit 1016, which can includea digital signal processor (DSP), a special-purpose processor, and/orthe like.

Computer-readable storage media reader 1012 can further be connected toa computer-readable storage medium 1010, together (and, optionally, incombination with storage device(s) 1008) comprehensively representingremote, local, fixed, and/or removable storage devices plus storagemedia for temporarily and/or more permanently containingcomputer-readable information. Communications system 1014 may permitdata to be exchanged with network 1024 and/or any other computerdescribed above with respect to system environment 1000.

Computer system 1000 may also comprise software elements, shown as beingcurrently located within working memory 1018, including an operatingsystem 1020 and/or other code 1022, such as an application program(which may be a client application, Web browser, mid-tier application,RDBMS, etc.). In an exemplary embodiment, working memory 1018 mayinclude executable code and associated data structures such as memorystructures used for processing authorization requests described above.It should be appreciated that alternative embodiments of computer system1000 may have numerous variations from that described above. Forexample, customized hardware might also be used and/or particularelements might be implemented in hardware, software (including portablesoftware, such as applets), or both. Further, connection to othercomputing devices such as network input/output devices may be employed.

Storage media and computer readable media for containing code, orportions of code, can include any appropriate media known or used in theart, including storage media and communication media, such as but notlimited to volatile and non-volatile, removable and non-removable mediaimplemented in any method or technology for storage of information suchas computer readable instructions, data structures, program modules, orother data. Examples of storage and computer-readable media include RAM,ROM, EEPROM, flash memory or other memory technology, CD-ROM, digitalversatile disk (DVD) or other optical storage, magnetic cassettes,magnetic tape, magnetic disk storage or other magnetic storage devices,or any other memory medium which can be used to store the desiredinformation and which can be read by a computer. Storage media andcomputer readable media may include non-transitory memory devices.

Although specific embodiments of the invention have been described,various modifications, alterations, alternative constructions, andequivalents are also encompassed within the scope of the invention.Embodiments of the present invention are not restricted to operationwithin certain specific data processing environments, but are free tooperate within a plurality of data processing environments.Additionally, although embodiments of the present invention have beendescribed using a particular series of transactions and steps, it shouldbe apparent to those skilled in the art that the scope of the presentinvention is not limited to the described series of transactions andsteps.

Further, while embodiments of the present invention have been describedusing a particular combination of hardware and software, it should berecognized that other combinations of hardware and software are alsowithin the scope of the present invention. Embodiments of the presentinvention may be implemented only in hardware, or only in software, orusing combinations thereof.

The specification and drawings are, accordingly, to be regarded in anillustrative rather than a restrictive sense. It will, however, beevident that additions, subtractions, deletions, and other modificationsand changes may be made thereunto without departing from the broaderspirit and scope as set forth in the claims.

That which is claimed is:
 1. A method comprising: storing, by a cloudinfrastructure system, a subscription order related to one or moreservices subscribed to by a customer, the one or more services providedby the cloud infrastructure system, the cloud infrastructure systemcomprising one or more computing devices; receiving, by a computingdevice from the one or more computing devices, a request to transferinformation between a first component and a second component in thecloud infrastructure system , the first component and the secondcomponent executed by the one or more computing devices; determining, bya computing device of the one or more computing devices, a firstsecurity zone for the first component and a second security zone for thesecond component; determining, by a computing device of the one or morecomputing devices, a first security level associated with the firstsecurity zone and a second security level associated with the secondsecurity zone; determining, by a computing device of the one or morecomputing devices, a way to transfer the information between the firstcomponent and the second component based upon security rulesinformation, wherein the security rules information specifies one ormore rules related to the transfer of the information between the firstsecurity level and the second security level; and determining that thetransfer of the information from the first component to the secondcomponent is to be performed by pushing the information from the firstcomponent to the second component if the second security levelassociated with the second component is same as or lower than the firstsecurity level associated with the first component.
 2. The method ofclaim 1, wherein pushing the information from the first component to thesecond component comprises invoking a synchronous write API of thesecond component.
 3. The method of claim 1, wherein pushing informationfrom the first component to second component comprises publishinginformation to a queue in the second component, wherein an interactionbetween the first component and the second component is asynchronous. 4.A method comprising: storing, by a cloud infrastructure system, asubscription order related to one or more services subscribed to by acustomer, the one or more services provided by the cloud infrastructuresystem, the cloud infrastructure system comprising one or more computingdevices; receiving, by a computing device from the one or more computingdevices, a request to transfer information between a first component anda second component in the cloud infrastructure system, the firstcomponent and the second component executed by the one or more computingdevices; determining, by a computing device of the one or more computingdevices, a first security zone for the first component and a secondsecurity zone for the second component; determining, by a computingdevice of the one or more computing devices, a first security levelassociated with the first security zone and a second security levelassociated with the second security zone; determining, by a computingdevice of the one or more computing devices, a way to transfer theinformation between the first component and the second component basedupon security rules information, wherein the security rules informationspecifies one or more rules related to the transfer of informationbetween the first security level and the second security level; anddetermining that the transfer of information from the first component tothe second component is to be performed by pulling the information bythe second component from the first component if the second securitylevel associated with the second component is greater than the firstsecurity level of the first component.
 5. The method of claim 4 whereinpulling the information further comprises the first component writingthe information to an output queue of the second component and thesecond component pulling the information from the output queue.
 6. Asystem comprising: one or more computing devices configurable to provideone or more services; a memory configurable to store a subscriptionorder related to the one or more services; and wherein a computingdevice from the one or more computing devices is configurable to:receive a request to transfer information between a first component anda second component in the cloud infrastructure system, the firstcomponent and the second component executed by the one or more computingdevices; determine a first security zone for the first component and asecond security zone for the second component; determine a firstsecurity level associated with the first security zone and a secondsecurity level associated with the second security zone; determine a wayto transfer the information between the first component and the secondcomponent based upon security rules information, wherein the securityrules information specifies one or more rules related to the transfer ofinformation between the first security level and the second securitylevel; and determine that the transfer of information from the firstcomponent to the second component is to be performed by pushing theinformation from the first component to the second component if thesecond security level associated with the second component is same as orlower than the first security level associated with the first component.7. The system of claim 6, wherein the computing device is configured topush the information from the first component to the second component byinvoking a synchronous write API of the second component.
 8. The systemof claim 6, wherein the computing device is configured to pushinformation from the first component to second component by publishinginformation to a queue in the second component, wherein an interactionbetween the first component and the second component is asynchronous. 9.The system of claim 6, wherein the computing device is configured toassign at least one of an existing security zone with an existingsecurity level or a new security zone with a new security level to a newcomponent in the cloud infrastructure system.
 10. The system of claim 6,wherein the computing device is configured to update at least one of asecurity zone or a security level of the one or more components in thecloud infrastructure system.
 11. A system comprising: one or morecomputing devices configurable to provide one or more services; a memoryconfigurable to store a subscription order related to the one or moreservices; and wherein a computing device from the one or more computingdevices is configurable to: receive a request to transfer informationbetween a first component and a second component in the cloudinfrastructure system, the first component and the second componentexecuted by the one or more computing devices; determine a firstsecurity zone for the first component and a second security zone for thesecond component; determine a first security level associated with thefirst security zone and a second security level associated with thesecond security zone; determine a way to transfer the informationbetween the first component and the second component based upon securityrules information, wherein the security rules information specifies oneor more rules related to the transfer of information between the firstsecurity level and the second security level; and determine that thetransfer of information from the first component to the second componentis to be performed by pulling the information by the second componentfrom the first component if the second security level associated withthe second component is greater than the first security level of thefirst component.
 12. A computer-readable memory storing a plurality ofinstructions executable by one or more processors, the plurality ofinstructions comprising: instructions that cause at least one processorfrom the one or more processors to store a subscription order related toone or more services from a set of services subscribed to by a customer;instructions that cause at least one processor from the one or moreprocessors to receive a request to transfer information between a firstcomponent and a second component in the cloud infrastructure system, thefirst component and the second component executed by one or morecomputing devices; instructions that cause at least one processor fromthe one or more processors to determine a first security zone for thefirst component and a second security zone for the second component;instructions that cause at least one processor from the one or moreprocessors to determine a first security level associated with the firstsecurity zone and a second security level associated with the secondsecurity zone; instructions that cause at least one processor from theone or more processors to determine a way to transfer the informationbetween the first component and the second component based upon securityrules information, wherein the security rules information specifies oneor more rules related to the transfer of the information between thefirst security level and the second security level; instructions thatcause at least one processor from the one or more processors todetermine that the transfer of information from the first component tothe second component is to be performed by pushing the information fromthe first component to the second component if the second security levelassociated with the second component is same as or lower than the firstsecurity level associated with the first component; and instructionsthat cause at least one processor from the one or more processors todetermine that the transfer of information from the first component tothe second component is to be performed by pulling the information bythe second component from the first component if the second securitylevel associated with the second component is greater than the firstsecurity level of the first component.
 13. The computer-readable memoryof claim 12 wherein the instructions that cause at least one processorfrom the one or more processors to push the information from the firstcomponent to the second component comprises instructions to invoke asynchronous write API of the second component.
 14. The computer-readablememory of claim 12 wherein the instructions that cause at least oneprocessor from the one or more processors to pull the informationfurther comprise instructions for the first component to write theinformation to an output queue of the second component and the secondcomponent to pull the information from the output queue.